-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Swift: upgrade to 5.9 #14261
Swift: upgrade to 5.9 #14261
Conversation
fec24b9
to
1bd3b91
Compare
645a3d6
to
8b55cea
Compare
e63cd58
to
f3f244c
Compare
1ab4a21
to
a96ac14
Compare
992869e
to
00235df
Compare
00235df
to
2b7ce23
Compare
swift/schema.py
Outdated
|
||
class SingleValueStmtExpr(Expr): | ||
""" | ||
An expression that may wrap a statement which produces a single value. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"may" makes it sound like the statement would be optional. Maybe
An expression that may wrap a statement which produces a single value. | |
An expression that wraps a statement which produces a single value. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's what the docs from compiler sources said 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, then we should probably double-check whether Stmt
should not be optional
(I would be surprised if it could though). If not, then I would drop the may
regardless of the internal compiler docs (which by the way we shouldn't really copy 😉).
swift/ql/test/extractor-tests/generated/expr/SingleValueStmtExpr/MISSING_SOURCE.txt
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The library changes and upgrade / downgrade scripts LGTM.
swift/ql/test/library-tests/dataflow/flowsources/CONSISTENCY/CfgConsistency.expected
Outdated
Show resolved
Hide resolved
I'm happy, once @redsun82 and the checks and the DCA job are all happy. |
|
AFAICT, currently we only have space for QL-related change notes. I'd like to include a note saying that we now support Swift 5.9, but previously I had to talk to a release manager to make this happen.
For sure, I hope this one gets in first though 😅 |
.../test/extractor-tests/generated/expr/SingleValueStmtExpr/CONSISTENCY/CfgConsistency.expected
Outdated
Show resolved
Hide resolved
More or less this. From the library perspective, there is a new class, so it's probably worth mentioning that. |
I'll do in the followup PR then, I don't want to restart the whole CI process for this PR. (unless there is some other changes need to happen here). |
I feel that the library change notes are an appropriate place to describe extractor changes (i.e. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is ready to merge. Please check that @redsun82 agrees before merging.
…value-stmt-expr Swlft: fix CFG for SingleValueStmtExpr
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the terrific work on this!
No description provided.